fix(deps): update module github.com/modelcontextprotocol/go-sdk to v1.6.1#151
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update module github.com/modelcontextprotocol/go-sdk to v1.6.1#151renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/github.com-modelcontextprotocol-go-sdk-1.x
branch
from
98f2e82 to
4d30a57
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.4.1→v1.6.1Release Notes
modelcontextprotocol/go-sdk (github.com/modelcontextprotocol/go-sdk)
v1.6.1Compare Source
This release adds an MCPGODEBUG flag to opt out of the Content-Type check on POST requests.
Behavior Changes
Prior to v1.6.0 (v1.4.0...v1.5.0), the Content-Type check on POST requests was gated by the same
disablecrossoriginprotectionMCPGODEBUG flag as the cross-origin protection. In v1.6.0, the cross-origin protection was disabled by default (replaced by the opt-inenableoriginverificationflag), but the Content-Type check was kept on unconditionally, leaving no way to disable it.This release restores an escape hatch for both the Streamable HTTP and SSE transports: setting
MCPGODEBUG=disablecontenttypecheck=1skips theContent-Type: application/jsonvalidation on POST requests.See #957.
What's Changed
Full Changelog: modelcontextprotocol/go-sdk@v1.6.0...v1.6.1
v1.6.0Compare Source
This release is equivalent to v1.6.0-pre.1. Thank you to those who tested the pre-release.
In this release we introduce several smaller fixes and improvements, and we started working for release 2026-06-30. The main new feature is the introduction of
ClientCredentialsHandlerfor OAuth client credentials grant.Add
ClientCredentialsHandlerfor OAuth client credentials grantAdded
ClientCredentialsHandlerimplementingauth.OAuthHandlerusing the OAuth 2.0 Client Credentials grant (RFC 6749 Section 4.4) for service-to-service authentication with pre-registered credentials.2026-06-30 Release related PRs
feat: add automatic application_type inference by @guglielmo-san in #904
New
application_typefield is added to theClientRegistrationMetadatafor DynamicClientRegistration. If not specified, theapplication_typewill be inferred from the RedirectURIs. This implements SEP-837.feat: HTTP Header Standardization for method and name by @guglielmo-san in #907
By mirroring key fields from the JSON-RPC payload into HTTP headers, network intermediaries such as load balancers, proxies, and observability tools can route and process MCP traffic without deep packet inspection, reducing latency and computational overhead. This partially implements SEP-2243.
Behavior Changes
SetErrorBehavior ChangePreviously the
SetErrormethod onCallToolResultalways overwrote theContentfield with the error text. NowSetErrorpreserves the existing value if it has already been populated. You can restore the previous behavior by setting the environment variableseterroroverwrite=1.Cross-Origin Protection Default Change
Previously (v1.4.1-v1.5.0) default (zero-value) cross-origin protection was applied when
CrossOriginProtectioninStreamableHTTPOptionswasnil. Now cross-origin protection is not enabled by default whenCrossOriginProtectionis nil.You can restore the previous behavior (enable by default) by setting
enableoriginverification=1.disablecrossoriginprotectionwas replaced byenableoriginverificationafter the default was changed to not enable cross-origin protection.jsonescapingoption was removed, according to plan.Other Changes to the SDK
ServerSession.startKeepaliveby @begelundmuller in #856New Contributors
Full Changelog: modelcontextprotocol/go-sdk@v1.5.0...v1.6.0-pre.1
v1.5.0Compare Source
This release is equivalent to v1.5.0-pre.1. Thank you to those who tested the pre-release.
In this release we introduce important enhancements to the client-side OAuth flows. We also introduce several smaller fixes and improvements.
Stabilization of client-side OAuth APIs
As previously communicated, we're stabilizing the client-side OAuth APIs in
v1.5.0. This means that themcp_go_client_oauthbuild tag will no longer be required to compile the functionality and standard backward compatibility guarantees apply from now on.Compared to the experimental support published in
v1.4.0, we made some backwards incompatible changes:auth.AuthorizationCodeHandlerConfig.AuthorizationCodeFetcher's type was changed fromfunc(context.Context, *auth.AuthorizationArgs) (*auth.AuthorizationResult, error)toauth.AuthorizationCodeFetcherwhich is a reusable definition carrying the same underlying function type.auth.AuthorizationCodeHandlerConfig.PreregisteredClientConfigwas removed and replaced withauth.AuthorizationCodeHandlerConfig.PreregisteredClientwhich uses a newly introducedoauthex.ClientCredentialstype. The type used previously (auth.PreregisteredClientConfig) has been removed.authandoauthexpackages.Enterprise Managed Authorization support added
Support for Enterprise Managed Authorization has been added to
auth/extauthpackage. Huge thanks to @radar07 for the implementation!Note: this support is part of an official MCP extension and is not part of the core protocol. The support of this functionality is not covered by the principles defined in SDK tiers.
Other changes to the SDK
New Contributors
Full Changelog: modelcontextprotocol/go-sdk@v1.4.1...v1.5.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.